Present:  Jim, Doug P, Chris S, Chris P, John R, Brent, Bill

General

•  Be sure to check out the fantastic job Kim FB is doing on the CMORE Drifter Blog.
• Kelly Lincetum from ASU may be coming out next week to go on the Zephyr and collect water.  ASU needs 'background' and this would give them a window into foundational oceanography, and perhaps give a better appreciation of sampling issues as it relates to their PCR efforts.  We may have a big 'filter-fest' and save some for us.

ESP User Group Meeting (Sep 27-29, 2011)

• This meeting will discuss G2 items only.
• Chris S will give high-level overview.  John R high level overview of L+O paper and BloomX update.  Chris P high level PCR (not water quality)
• MBARI is finished at 1:30 on Tuesday, although there is an afternoon session Weds afternoon at Spyglass.  May have Chris p, Bill, Doug attend and talk about pier stuff.
• We will suggest shortening the panel discussion Tuesday at MBARI and make room for Brent to talk about comms. (Jim to contact Spyglass)
• Also suggest moving Kevin's GUI discussion to earlier.
•  Spyglass needs arrays for this meeting.  We do not have.  They should contact WHOI.
• Will email Melancon/Shana a copy of the Nov, 2009 Fluidics path diagram.

Core

• Pier deployment on schedule for Friday, October 14.  Will wait until Roman returns Sep 26 to start pinging Pier guys for access to set-up radios
• Latest SW changes for combined array/PCR have introduced very BIG script changes.  These changes will need to be pushed out to the upcoming users who want to do both PCR and SHA.

G3 Development

• Functional Requirements document has been updated and sent out to team for comment. Please return comments by end of week and Jim will incorporate. Req's document will be kept on Confluence with date stamps so most recent will be easy to find.
• Some confusion about what separates the 'Sampler' module and 'core' module (analytical module seems well-defined). Some effort needs to be expended to define the Sampler a little better.
• This new 3-box division (sampler, core, analytical module) makes some sense with regards to breaking up labor, but careful attention needs to be paid to the where the 'fences' are between boxes and subsequent effects on requirements so each box will play well with its downstream neighbor.